Triple
T19468575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leading Arm |
E487062
|
entity |
| Predicate | hasPhysicalProcessOrigin |
P56832
|
FINISHED |
| Object | tidal stripping |
—
|
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: tidal stripping | Statement: [Leading Arm, hasPhysicalProcessOrigin, tidal stripping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalProcessOrigin Context triple: [Leading Arm, hasPhysicalProcessOrigin, tidal stripping]
-
A.
hasRealWorldOrigin
Indicates that something is derived from, based on, or directly connected to an actual entity, event, or source in the real world.
-
B.
physicalOrigin
chosen
Indicates that one entity is the place or source from which another entity physically originates or comes into existence.
-
C.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
D.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
-
E.
hasCollisionalOrigin
Indicates that one entity originates from, or is the result of, a collision or collisional event involving 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e4b230819097c8804ee91988ea |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.