Triple
T37056775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lines |
E917211
|
entity |
| Predicate | hasCollaborativeFeatures |
P100197
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lines, hasCollaborativeFeatures, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollaborativeFeatures Context triple: [Lines, hasCollaborativeFeatures, yes]
-
A.
isCollaborative
Indicates that two or more entities work together jointly toward a shared goal or outcome.
-
B.
supportsCollaborationFeature
chosen
Indicates that one entity provides or enables a collaboration-related feature for another entity or within a system.
-
C.
featuresCollaboration
Indicates that one entity includes, showcases, or is characterized by a collaborative effort or partnership with another entity.
-
D.
usesCollaboration
Indicates that one entity employs or relies on collaborative methods, tools, or partnerships with another entity to achieve a shared goal or perform an activity.
-
E.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.