Triple
T25063485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ContainerMembershipProperty |
E627722
|
entity |
| Predicate | isAbstractClassFor |
P145275
|
FINISHED |
| Object | rdf:_n style properties |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: rdf:_n style properties | Statement: [ContainerMembershipProperty, isAbstractClassFor, rdf:_n style properties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAbstractClassFor Context triple: [ContainerMembershipProperty, isAbstractClassFor, rdf:_n style properties]
-
A.
isClassOf
Indicates that one entity is a class or category to which another entity belongs or is an instance of.
-
B.
hasAbstractType
chosen
Indicates that an entity is associated with or classified under a more general, conceptual type rather than a concrete or specific instance.
-
C.
isShortForClass
Indicates that one class name is an abbreviation or shortened form of another class name.
-
D.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
-
E.
includesAbstract
Indicates that one entity contains or incorporates the abstract or summary section of another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4599b7ff081909862edeae57c2c2d |
completed | May 1, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:10 a.m.