Triple
T587781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On Physical Lines of Force |
E15196
|
entity |
| Predicate | buildsOnConcept |
P7125
|
FINISHED |
| Object | Faraday's lines of force |
—
|
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: Faraday's lines of force | Statement: [On Physical Lines of Force, buildsOnConcept, Faraday's lines of force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildsOnConcept Context triple: [On Physical Lines of Force, buildsOnConcept, Faraday's lines of force]
-
A.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
B.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
C.
isBasedOn
chosen
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
D.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
-
E.
endsOn
Indicates that one entity terminates or concludes precisely at the boundary or endpoint 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b9d1e68819096a9b5e7b2e83d6e |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494ca68448190a516b9c3525d8916 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.